Release 10.1A: OpenEdge Getting Started:
New and Revised Features

Preface

This Preface contains the following sections:

Purpose
Audience
Organization
Typographical conventions
Examples of syntax descriptions
Examples of syntax diagrams (SQL)

Purpose

OpenEdge Getting Started: New and Revised Features briefly describes new features and changes to existing features introduced in Progress® OpenEdge™ Release 10.1A and guides you to where you can find more detailed information about these changes in the documentation set. The Release 10.1A documentation set references include:

Product manuals — Identified by the Manual label in tables throughout this book.
HTML-based online help — Identified by the HTML online help label in tables throughout this book.
Web papers — Identified by the Web paper label in tables throughout this book.

You can access the OpenEdge Web paper from the following Web site: http://www.progress.com/products/documentation. If you are viewing the pdf version of this document, click the Web paper title to go directly to the Web site.

Release Notes — Provided in two formats: a hard-copy version included in the Release 10.1A product media kit and an online version available after the product is installed.

Audience

This guide is primarily intended for OpenEdge application developers and system administrators who are upgrading their license to Release 10.1A from Release 10.0B. It is also a good information source for other existing Release 10.0B users who want to know more about the new and changed features available in Release 10.1A.

Organization

Chapter 1 "What’s New"

Presents brief explanations of new and enhanced features introduced in Release 10.1A, references places within the documentation set where more detailed feature information can be found, and provides a documentation map of Release 10.1A arranged by technology.

Chapter 2 "Feature Comparisons"

Describes how changed features in OpenEdge Release 10.1A differ from how they functioned previous releases. The comparisons describe possible changes in behavior of a tool or application code, and describe changes in documentation.

Typographical conventions

This manual uses the following typographical conventions:

Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
Fixed width	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
Fixed-width italics	Fixed-width italics indicate variables in syntax statements.
Fixed-width bold	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.
Period (.) or colon (:)	All statements except DO, FOR, FUNCTION, PROCEDURE, and REPEAT end with a period. DO, FOR, FUNCTION, PROCEDURE, and REPEAT statements can end with either a period or a colon.
[ ]	Large brackets indicate the items within them are optional.
[ ]	Small brackets are part of the Progress 4GL language.
{ }	Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams.
{ }	Small braces are part of the Progress 4GL language. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure.
|	A vertical bar indicates a choice.
...	Ellipses indicate repetition: you can choose one or more of the preceding items.

Examples of syntax descriptions

In this example, ACCUM is a keyword, and aggregate and expression are variables:

Syntax

ACCUM aggregate expression

FOR is one of the statements that can end with either a period or a colon, as in this example:

FOR EACH Customer:   DISPLAY Name. END.

In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:

Syntax

DISPLAY [ STREAM stream ] [ UNLESS-HIDDEN ] [ NO-ERROR ]

In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item:

Syntax

INITIAL [ constant [ , constant ] ]

A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example:

Syntax

{ &argument-name }

In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them:

Syntax

PRESELECT [ EACH | FIRST | LAST ] record-phrase

In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas:

Syntax

MAXIMUM ( expression , expression [ , expression ] ... )

In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed:

Syntax

MESSAGE { expression | SKIP [ ( n ) ] } ...

In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }:

Syntax

{ include-file     [ argument | &argument-name = "argument-value" ] ... }

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

In this example, WITH is followed by six optional items:

Syntax

WITH [ ACCUM max-length ] [ expression DOWN ]   [ CENTERED ] [ n COLUMNS ] [ SIDE-LABELS ]   [ STREAM-IO ]

Complex syntax descriptions with both required and optional elements

Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements).

In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets:

Syntax

ASSIGN   { [ FRAME frame ] { field [ = expression ] }             [ WHEN expression ] } ...        | { record [ EXCEPT field ... ] }

Examples of syntax diagrams (SQL)

In this example, GRANT, RESOURCE, DBA, and TO are keywords. You must specify RESOURCE, DBA, or both, and at least one user_name. Optionally you can specify additional user_name items; each subsequent user_name must be preceded by a comma:

Syntax

GRANT { RESOURCE, DBA } TO user_name [, user_name ] ... ;

This excerpt from an ODBC application invokes a stored procedure using the ODBC syntax { call procedure_name ( param ) }, where braces and parentheses are part of the language:

Syntax

proc1( param, "{ call proc2 (param) }", param);

In this example, you must specify a table_name, view_name, or synonym, but you can choose only one. In all SQL syntax, if you specify the optional owner_name qualifier, there must not be a space between the period separator and table_name, view_name, or synonym:

Syntax

CREATE [ PUBLIC ] SYNONYM synonym   FOR [ owner_name.]{table_name |view_name |synonym } ;

In this example, you must specify table_name or view_name:

Syntax

DELETE FROM [ owner_name.]{table_name |view_name }   [ WHERE search_condition ] ;

In this example, you must include one expression (expr) or column position (posn), and optionally you can specify the sort order as ascending (ASC) or descending (DESC). You can specify additional expressions or column positions for sorting within a sorted result set. The SQL engine orders the rows on the basis of the first expr or posn. If the values are the same, the second expr or posn is used in the ordering:

Syntax

ORDER BY { expr | posn } [ ASC | DESC ]   [ , [ { expr | posn } [ ASC | DESC ] ] ... ]

Long syntax descriptions split across lines

Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order.

In this example, CREATE VIEW is followed by several optional items:

Syntax

CREATE VIEW [ owner_name.]view_name   [ ( column_name [, column_name ] ... ) ]   AS [ ( ] query_expression [ ) ] [ WITH CHECK OPTION ] ;